	8/2/1988

		IMPORTANT INFORMATION ON THE ROCHESTER SIMULATOR, MAC VERSION
		-------------------------------------------------------------
		
		
	1. There are 2 disks in all. For an overview of what's where see 'GUIDE'.
	
	2. All the code is in MPW C 3.0. If you don't have MPW this is all useless to you.
	
	3. The source files are in 'Rochester 2:src:uniproc'. Not all the functions of
		the Rochester Connectionist Simulator have been ported to the Mac. That's
		why you need to put the Unix .h files from 'Rochester 2:src:special includes'
		in your MPW:Interfaces:CIncludes folder. This is so that the simulator
		compiles.
		
	4. You need to change some of the '#include ..' statements from the source
		files. My hard disk is called "Stupido", so you have to change that to
		whatever your hard disk is called. I suggest you put everything from the
		3 disks in one folder. This way you won't have to change the '#include ..'
		statements extensively.
		
	5. If you have LaTeX you can print out your own copy of the Rochester Simulator
		manual. All the necessary files are in 'Rochester 1:doc'. If you don't have
		LaTeX you can talk to the people at the Univ. of Rochester about sending you
		a manual. See the 'Read me' file for addresses and so on.
		
	6. The Rochester simulator that will result after compilation will be an MPW
		tool and not an application.

	7. An example makefile for MPW is in 'Rochester 2:example:4color:sim.4color.make'.
		That's how all makefiles for a simulator should basically look. Compilation
		with the '-m' flag is required because of the large amount of global
		variables that the Rochester simulator employs.
		
	8. VERY IMPORTANT! The Unix version of the simulator had a Bourne shell script
		file which made the whole thing. In particular, it looked in all the compiled
		code for function names and made a little C function to enter them in the 
		Rochester name table. Because of the way Rochester works, every function that
		the user wants to access (by 'call'ing it or assigning a particular unit
		or site function, etc.) has to be in the name table. On the Mac it would be
		very hard to make such a makefile. That's why you have to enter those
		functions in the name table yourself. This is not so horrible. If you look
		in the 'Rochester 2:src:uniproc:names.c' file, at the very end of it you will
		see the 'si_cmd_bind_func()' and the 'si_user_bind_func()'. Whatever new
		function you wrote that you want to access, you have to add a line in the 
		'si_user_bind_func()' of the type 'AddItemToTable ...'. Then you can 'call'
		this function or assign it as a unit function, etc. You will, of course,
		also have to declare this function in the 'names.c' file.
		There are also two files which will create the 'si_cmd_bind_func()' and the
		'si_user_bind_func()' when presented with a list of function names. They are
		in 'Rochester 2:src:tools'.
		
	9. Included 1n 'Rochester 2:src:Linda' is Linda-C code for a parallel version of
		the simulator. You will not be able to use this unless you have a machine with
		an implementation of Linda-C. Read the 'Info on parallel version' file for
		details.
		
 ! 10. Please read the license agreement on the last page of the User Manual (in the
		'Rochester 1:doc' folder. Also all Linda-C code (parts of the 'Rochester 2:src:
		Linda:simain.c' file) are (C) 1989 Chorus Supercomputer Inc. The Linda-C code
		is ditributed free, for research purposes. Please include an appropiate
		citation in the publication of results obtained with it.